Description

This PR moves the inner blocks container for the Post Template block to a separate component, to ensure that the result of useInnerBlocksProps is always applied to same React node relative to the call to the hook.

I'm not 100% sure why this fixes it, but it resolves the following issue:

Before: in a long Post Template block within a long query loop (e.g. within the Index template of the TT1-Blocks theme with 2+ published posts) if you click on a block within the first post within the loop, then scroll down to click on a similar block within another post within the loop, then the scroll position of the editor moves when the parent Post Template block is selected.

After: on click, the selection changes, but the scroll position does not move away unexpectedly.

How has this been tested?

1. Ensure your site has at least two published posts
2. With an FSE theme like TT1-Blocks active, go to the site editor and view a list of posts within a Query Loop block (containing the Post Template block)
3. Click on a block within the Post Template block of the query loop (e.g. click on Post Content)
4. Scroll down the page and click on a similar block in the next post within the query loop
5. Before this PR, note that the scroll position of the page moves when you select the block
6. After this PR, the scroll position shouldn't change

Note: there is a separate issue that on the first click, the Post Template block is selected instead of the target block. That's logged in issue #35944 and is to do with the way the Post Template block only renders one post at a time as live editable blocks (the other posts are rendered as BlockPreviews). This PR only seeks to address the scrolling issue

Screenshots

Note: in the before screenshot, after clicking the similar block in the next post, the viewport is scrolled to the bottom of the page unexpectedly. In the After screenshot, the viewport is not scrolled unexpectedly (but it still takes a couple of clicks to activate the desired block as noted in #35944)

Before	After

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).